Hi All...
Having been forced to by my ISP to cancel my cable internet and swap to a new fibre connection, I have come across an interesting issue.
The new fibre service has done away with my tradional phone line, and substituted it with a VOIP line. If I plug the phone into the ISP supplied router/modem, and then plug that into the ER8, everything works OK. I can dial in and out.
But runnning the same VOIP setting on a Cisco SPA112, and I can't dial out. But it will receive calls.
The only difference I can see is in the INVITE packet sent from me, to initiate the call. On the ISP modem, within the message header I found this:
Via: SIP/2.0/UDP 192.168.5.132;branch=z9hG4bK7995f79322e971d3f.e2dfd83efa623033b;rport Transport: UDP Sent-by Address: 192.168.5.132 Branch: z9hG4bK7995f79322e971d3f.e2dfd83efa623033b
RPort: rport Route: <sip:210.49.224.68:5060;lr> Route URI: sip:210.49.224.68:5060;lr Route Host Part: 210.49.224.68 Route Host Port: 5060 Route URI parameter: Ir Route: <sip:210.49.224.68:5060;transport=udp;lr> Route URI: sip:210.49.224.68:5060;transport=udp;Ir Route Host Part: 210.49.224.68 Route Host Port: 5060 Route URI parameter: transport=udp Route URI parameter: Ir
But the Cisco SPA112 only has this:
Via: SIP/2.0/UDP 192.168.5.57:5060;branch=z9hG4bK-elc282ba Transport: UDP Sent-by Address: 192.168.5.57 Sent-by port: 5060 Branch: z9hG4bK-elc282ba
There is no route information.
I am wondering if this is an issue caused by the ER8 stripping something out during the initial SIP registration, or simply a Cisco setup issue, where it is unable to setup an outgoing RTP stream.
It looks like it tries to setup the call in the same way as the ISP modem.
Any ideas..???
Thanks..!!