Odd SIP channel activity?

Forums › VoIP › Odd SIP channel activity?

mjb

922 posts

Ultimate Geek
+1 received by user: 21

Trusted

Topic # 31948 6-Apr-2009 12:54

So I made the cutover to using Asterisk at home, instead of a single device connecting to iTalk.

I'm seeing odd activity with SIP channels, with items appearing and disappearing quite frequently (CallID is changing), always with the same last message:

host*CLI> sip show channels
Peer User/ANR Call ID Seq (Tx/Rx) Format Hold Last Message
203.184.16.2 (None) 6e34102d1d5 00101/00102 0x0 (nothing) No Rx: OPTIONS
1 active SIP channel

An example from history:

host*CLI> sip show history 7068d0dc4003f59f7b6083cd71fc3ea0@203.184.16.2
* SIP Call
1. Rx OPTIONS / 102 OPTIONS / sip:s@10.x.y.z
2. TxResp SIP/2.0 / 102 OPTIONS - 404 Not Found
3. SchedDestroy 32000 ms

Is this normal? is there anything I should do to correct this?

contentsofsignaturemaysettleduringshipping

joshp

205 posts

Master Geek
+1 received by user: 1

Trusted

WorldxChange

Reply # 205531 6-Apr-2009 13:13

An OPTIONS message is usually just a keep alive, I suspect this is what you are seeing, try doing an ngrep -d eth0 port 5060 and HOSTIPOFITALK

it should show you the actual SIP messages that are going out/coming in :)

http://wxc.co.nz

mjb

922 posts

Ultimate Geek
+1 received by user: 21

Trusted

Reply # 205534 6-Apr-2009 13:18

I beat you to it by about 30 seconds.

Adding:
exten => s,1,NoOp()

to my default context turned the result into a 200 OK, which confirmed my suspicions that it was simply a keepalive (after refining google search to find a single message in a mailing list thread that was implying such).

Thanks for the response :)

Now to nut out the outgoing dial plan :(. There are way too many patterns to match sadly. I wish there was a definitive list somewhere (is there?).

contentsofsignaturemaysettleduringshipping

sbiddle

27140 posts

Uber Geek
+1 received by user: 6579

Moderator

Trusted

Biddle Corp

Lifetime subscriber

Reply # 205537 6-Apr-2009 13:34

mjb: I beat you to it by about 30 seconds.

Adding:

exten => s,1,NoOp()

to my default context turned the result into a 200 OK, which confirmed my suspicions that it was simply a keepalive (after refining google search to find a single message in a mailing list thread that was implying such).

Thanks for the response :)

Now to nut out the outgoing dial plan :(. There are way too many patterns to match sadly. I wish there was a definitive list somewhere (is there?).

How many VoIP providers are you using? If you're only using one there is no real need for a complex dialplan, just use

X.

and all calls will be routed out via iTalk. If you have multiple VoIP providers then you do need to create one for each provider which is very simple when you get the hang of it.

mjb

922 posts

Ultimate Geek
+1 received by user: 21

Trusted

Reply # 205538 6-Apr-2009 13:41

sbiddle: How many VoIP providers are you using? If you're only using one there is no real need for a complex dialplan, just use

X.

and all calls will be routed out via iTalk. If you have multiple VoIP providers then you do need to create one for each provider which is very simple when you get the hang of it.

Just the one. I had thought of doing that.. but wasn't sure of the implications. The dial plan is processed in order? so rules before that for dialing each device around the house will be honoured first? A'la:

exten => 20,1,Dial(${HOUSE},,rtT)
exten => 21,1,Dial(${CORDLESS},,tT)
exten => 22,1,Dial(${OFFICE},,tT)
exten => 23,1,Dial(${LOUNGE},,tT)

exten => *99,1,VoicemailMain

exten => _X.,1,Dial(SIP/iTalk/${EXTEN},30,T)

contentsofsignaturemaysettleduringshipping